<text>A HyperCard 2.0 add-on to increase Tabbing speed</text>
</content>
<content>
<layer>card</layer>
<id>3</id>
<text>Version 1.03 March 1, 1992
Written by John Miller
Copyright © 1990-1992 Symplex Systems
Burnaby, British Columbia, Canada</text>
</content>
<content>
<layer>card</layer>
<id>4</id>
<text>HyperCard 2.0 has a performance problem when the user presses the Tab key to move from field to field. This problem is most severe on slower Macintosh models: the Mac Plus, SE, or Classic. On large cards with many fields, the user might have to wait 2 or 3 seconds each time the Tab is pressed. The FastTab XCMD reduces tabbing time so that HyperCard is useful for cards with many fields.</text>
</content>
<content>
<layer>card</layer>
<id>10</id>
<text>1.03b2</text>
</content>
<name></name>
<script></script>
</card>
card_4709.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
if selChunk is not empty then fasttab "select" && selChunk
-- if selChunk is not empty then select selChunk
-- put the ticks - starttime into tabtime
end mouseDown
</script>
</part>
<part>
<id>43</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>165</left>
<top>69</top>
<right>360</right>
<bottom>91</bottom>
</rect>
<style>radiobutton</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>9</textSize>
<textStyle>bold</textStyle>
<name>Use FastTab</name>
<script>on mouseDown
global useFast
-- global tabtime
-- put the ticks into starttime
put the selectedChunk into selChunk
put the hilite of me into oldHilite
set the hilite of me to true
repeat while the mouse is down
if the mouseLoc is within the rect of me then
set the hilite of me to true
else
set the hilite of me to oldHilite
end if
end repeat
get the hilite of me
put it into useFast
set the hilite of card button id 41 to not it
if selChunk is not empty then fasttab "select" && selChunk
-- if selChunk is not empty then select selChunk
-- put the ticks - starttime into tabtime
end mouseDown
</script>
</part>
<part>
<id>44</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>414</left>
<top>0</top>
<right>446</right>
<bottom>32</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>26425</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>GoRight</name>
<script>on mouseUp
visual wipe left fast
go next card
end mouseUp</script>
</part>
<part>
<id>45</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>0</left>
<top>0</top>
<right>33</right>
<bottom>35</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>902</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>GoLeft</name>
<script>on mouseUp
visual wipe right fast
go previous card
end mouseUp</script>
</part>
<part>
<id>46</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>338</left>
<top>21</top>
<right>369</right>
<bottom>49</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>8980</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Help</name>
<script>on mouseUp
get the visible of card field "about"
set the visible of card field "about" to not it
set the visible of the variable watcher to it
end mouseUp</script>
</part>
<part>
<id>47</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>2</left>
<top>46</top>
<right>511</right>
<bottom>548</bottom>
</rect>
<style>shadow</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>About</name>
<script>on mouseDown
send mouseUp to button "help"
end mouseDown</script>
</part>
<content>
<layer>background</layer>
<id>21</id>
<text>312.25</text>
</content>
<content>
<layer>background</layer>
<id>1</id>
<text>Bobby Smith
432 Integer Street
Portland
XQ12876
</text>
</content>
<content>
<layer>background</layer>
<id>25</id>
<text>1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30</text>
</content>
<content>
<layer>background</layer>
<id>26</id>
<text>Click the "?" button for more information.
The global variable TabTime shows # of ticks.
Click the "?" button for more information.
This is a description of this very nice item.
This is a shorter description
Click the "?" button for more information.
Click the "?" button for more information.
description of last item</text>
</content>
<content>
<layer>background</layer>
<id>27</id>
<text>MV9878NB
rx7
123123
345345
1233
MX765-987
</text>
</content>
<content>
<layer>background</layer>
<id>28</id>
<text>10876.00
12.00
123.00
10.32
34.00
12.00
12.00</text>
</content>
<content>
<layer>background</layer>
<id>29</id>
<text>2
5
1
2
3
2
2</text>
</content>
<content>
<layer>background</layer>
<id>30</id>
<text>21752.00
60.00
123.00
20.64
24.00
24.00</text>
</content>
<content>
<layer>background</layer>
<id>44</id>
<text>341.58</text>
</content>
<content>
<layer>background</layer>
<id>43</id>
<text>19.33</text>
</content>
<content>
<layer>background</layer>
<id>40</id>
<text>10.00</text>
</content>
<content>
<layer>background</layer>
<id>41</id>
<text>322.25</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Sounds Right</text>
</content>
<content>
<layer>background</layer>
<id>2</id>
<text>(604) 433-1795</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>John Smith </text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Peter Smith</text>
</content>
<content>
<layer>background</layer>
<id>46</id>
<text>Prod Mgr</text>
</content>
<content>
<layer>background</layer>
<id>7</id>
<text>May 11/90</text>
</content>
<content>
<layer>background</layer>
<id>8</id>
<text>May 11/90</text>
</content>
<content>
<layer>background</layer>
<id>9</id>
<text>May 20/90
</text>
</content>
<content>
<layer>background</layer>
<id>10</id>
<text>May 50/90</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>7779992</text>
</content>
<content>
<layer>background</layer>
<id>13</id>
<text>Product</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>10987.67</text>
</content>
<content>
<layer>background</layer>
<id>15</id>
<text>52</text>
</content>
<content>
<layer>background</layer>
<id>39</id>
<text>5% Discount</text>
</content>
<content>
<layer>card</layer>
<id>40</id>
<text>Example Card</text>
</content>
<content>
<layer>card</layer>
<id>39</id>
<text>
</text>
</content>
<content>
<layer>background</layer>
<id>51</id>
<text>Was not Changed</text>
</content>
<content>
<layer>card</layer>
<id>47</id>
<text>This example illustrates many points
1) Most of the fields default to the card's tabKey handler which simply calls either tabKey or fastTab, depending on the state of the radio button cluster.
2) To illustrate the difference in speed, timing code has been added that displays the number of ticks (1 tick = 1/60 second) required to perform the action. This value is stored in the global variable TabTime and can be seen in the Variable Watcher window.
3) The field "RentedTo" contains "closeField" and "exitField" handlers. The purpose of these handlers is to show that FastTab seems to handle correctly the case where changes are made to the card in an closeField or an exitField handler. (FastTab will not handle changes to cards that are made within an openField handler, but I suspect this is a rare case.)
The field scripts for the columns labelled "Daily Rental" and "Days" show a more realistic example of closeField handlers.
4) The six 30-line fields contain a special handler that attempts to provide a crude row and column capability. The relevance of this "row and column" script is that it calls FastTab with a parameter that uses HyperCard's "select" command.
5) The card shows the range of speedup possible. The fastest speedup is for the fields "TakenOut", "RentalStarts", "ExpectedReturn", InsuranceValue", etc. These fields have the least overhead when using FastTab. The fields at the top of the card are a bit slower because care has to be taken to deal with the overlapping fields (that is, the "Example" box). Finally, the six 30-line fields show the least speedup. The speed penalty is only incurred on those fields where the overhead is required. </text>
</content>
<content>
<layer>background</layer>
<id>45</id>
<text>2</text>
</content>
<content>
<layer>background</layer>
<id>3</id>
<text>0007198</text>
</content>
<name>Example</name>
<script>on closeCard
if the visible of card field "about" then
send mouseup to button "help"
end if
end closeCard
on makedots
put 0 into h
choose pencil tool
repeat while h < the right of this card
do "click at " & h & ",189"
add 32 to h
end repeat
end makedots
</script>
</card>
card_5326.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">he FastTab stack may be freely distributed as long as it is not modified and as long as it is not sold. User groups may charge their normal disk copying fees. Bulletin boards and other online services may charge their normal connection fees.
The FastTab XCMD is being distributed as shareware. The shareware fee is $14 for individual use. This allows a user to install the FastTab XCMD in any stack that he uses, but does not include the right to distribute stacks containing the FastTab XCMD.
To register, please send your shareware fee to the address at the end of this section. Please indicate that it is for registration of FastTab 1.03 and include your name and address (include e-mail addresses, if any). Registration implies that you have read and accepted the "</span><span class="style8">Disclaimer</span><span class="style1">" section.
</span></text>
</content>
<name>Registration, Distributio</name>
<script></script>
</card>
card_5388.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">o distribute the FastTab XCMD in any other stack requires a license from Symplex Systems. This applies to all distribution: internal or external, commercial or non-commercial. For more information, please contact Symplex Systems.
</span><span class="style8"> Symplex Systems
</span><span class="style16">
</span><span class="style6"> #1703 - 4134 Maywood Street Tel: (604) 433-1795
Burnaby, British Columbia Fax: (604) 430-8516
Canada Internet : john_miller@mindlink.bc.ca</span><span class="style17">
<text>I am only on AppleLink a few times a month. If you want to reach me quickly from AppleLink, address the message to "a347@mindlink.UUCP@internet#". This will send it to my internet mail address.
</text>
</content>
<name></name>
<script>on closeCard
hide card field "AppleLink"
end closeCard</script>
</card>
card_3747.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">ow to Use FastTab</span><span class="style7"></span><span class="style4"></span><span class="style2"></span><span class="style4"></span></text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text><span class="style14"></span><span class="style3">Using FastTab without parameters
</span><span class="style1">
The simplest use of FastTab is as a replacement for HyperCard 2.0's standard tabKey handler. After installing FastTab in a stack, add the following handler to the stack script.
</span><span class="style5">on tabKey
fastTab
end tabKey
</span><span class="style1">
The "</span><span class="style2">fastTab</span><span class="style1">" statement has the same effect as using "</span><span class="style2">send tabKey to HyperCard</span><span class="style1">" but is faster.
</span></text>
</content>
<name>How to Use FastTab</name>
<script></script>
</card>
card_3883.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">ow to Use FastTab </span><span class="style4">(cont.)</span></text>
</content>
<content>
<layer>card</layer>
<id>4</id>
<text>To be precise, it was designed for the normal use of the select command, where a piece of text in a field is being selected.
It is not intended for commands such as "select field 3" or "select button bob" which switch to the button or field tool from the browse tool.</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text><span class="style3">Using FastTab with a single parameter</span><span class="style1">
FastTab also can be invoked with a single argument. If present, this argument will be taken as a HyperTalk statement to do instead of "tabKey." For instance,
</span><span class="style5">
fastTab "select char 12 to 50 of field 2"
</span><span class="style1">will have the same effect as
</span><span class="style5">
send "select char 12 to 50 of field 2" to HyperCard
</span><span class="style1">
The optional parameter version of FastTab was designed and tested to increase the speed of the "select" command. It most likely will not work with other HyperTalk commands.
</span></text>
</content>
<name></name>
<script>on closeCard
hide card field "about select"
end closeCard</script>
</card>
card_9129.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
</span><span class="style1">If a section of the card is not being redrawn properly, you can specify optional rectangle parameters when calling FastTab.
</span><span class="style5">
FastTab "","50,45,100,200" -- invokes "tabkey" because
-- first parameter is blank
FastTab "select char 1 to 20 of field bob",rectVar
</span><span class="style2">More than one rectangle parameter can be specified. Anything within or overlapping the specified rectangles will be redrawn. If fields are within the rectangle, this means, of course, that some of the speedup created by FastTab will be lost.
</span><span class="style15">
</span><span class="style5">These rectangle parameters are meant primarily as a work-around for the "paint on the card layer" limitation which is described later.</span></text>
</content>
<name></name>
<script>on closeCard
hide card field "about select"
end closeCard</script>
</card>
card_7795.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
Following the convention for commands, FastTab returns results that indicate the success of the command. Scripts can call "the result" function after invoking FastTab to check for errors. An empty result string indicates "no error."
If HyperCard complains about the message that is passed as FastTab's first parameter, the result will be set to "Invalid message". If one of the optional rectangle parameters cannot be interpreted as a rectangle, the result will be set to "Invalid rectangle".
If FastTab is invoked with "!" or "?" as the optional parameter, FastTab will return a copyright notice in the result. A version number and copyright notice will also be placed in the message box.
</text>
</content>
<name>Error Results</name>
<script></script>
</card>
card_9370.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
Changes made to a card from an "openField" message handler likely will not be properly redrawn. Actually, I don't think this too great a limitation. In order, for instance, to put something into another field from an openField handler, a script has to jump through enough "selection saving and restoring" hoops that I think the construct will be sufficiently rare.
An openField handler that initializes global variables causes no problems.</span></text>
</content>
<name>Limitations and Workaroun</name>
<script></script>
</card>
card_9663.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">imitations and Workarounds </span><span class="style4">(cont.)</span></text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text><span class="style3">Paint on the card layer</span><span class="style1">
Unfortunately, here is where things get a bit trickier. The HyperCard image consists of four layers: the background paint layer, the background fields and buttons, the card layer, and the card fields and buttons. I have not found a case where background paint causes any problem, but there are things to watch when dealing with paint on the card layer.
</span></text>
</content>
<name></name>
<script></script>
</card>
card_9807.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">imitations and Workarounds </span><span class="style4">(cont.)</span></text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text><span class="style3">Leave holes for card fields and buttons</span><span class="style1">
Normally, after drawing the background layers, HyperCard draws the card paint layer and then draws the card fields and buttons "on top" of the card layer. All is groovy in the world. Unfortunately, FastTab comes along and says "No need to draw that field, or that field, or that button, ...." Suppose you have designed a card with a card paint layer that uses a grey pattern as a backdrop for some fields and buttons. The entire grey layer is redrawn but FastTab stops HyperCard from redrawing some of the buttons and field because they haven't changed. The result is that, under various conditions, some of the buttons and fields seem to "disappear."
</span></text>
</content>
<name></name>
<script></script>
</card>
card_10124.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">imitations and Workarounds </span><span class="style4">(cont.)</span></text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text><span class="style14"></span><span class="style3">Leave holes for card fields and buttons (cont.)</span><span class="style1">
</span><span class="style6">
</span><span class="style1">The workaround ΓÇö assuming you can't just put the paint in the background layer or use a white backdrop ΓÇö is to "cookie cut" holes in the paint layer wherever you are going to place a card button or field. That is, the card paint beneath any card field or car button should be set to "transparent" (under the Paint menu) white. The button below will do some of the cookie cutting for a card, but you may still have to do some touch-up around the outlines of some buttons (particularly transparent buttons with icons).
</span><span class="style6">
The button will prompt you to select the card image to cookie cut. You may want to make a copy of the card before cookie cutting: this will make it easier for you if you later decide to make changes to the card layout.
</span></text>
</content>
<name></name>
<script></script>
</card>
card_10281.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
The other problem with card paint is almost the exact opposite of the first problem: sometimes the paint image is not redrawn at all. Consider the cards below:
</span><span class="style6"> Figure 1: a single-card paint backdrop Figure 2: a background with an area
that doesn't cover all the fields. reserved for a different
picture on each card.</span></text>
</content>
<name></name>
<script></script>
</card>
card_11104.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
Figure 1 shows a case where there is a card paint layer backdrop, but it doesn't overlap every field. If the user tabs between the two bottom fields ΓÇö which don't overlap the paint backdrop ΓÇö the paint image may get erased. This problem may not even be noticed by the user until he scrolls with the Scroll windoid or tabs into one of the other fields, but it's there. An easy workaround for a custom crafted card such as Figure 1 is to use the pencil tool to put a single pixel dot at each of the four corners of the card. This ensures that the enclosing rectangle of the card picture overlaps all of the fields and that, therefore, the card picture will be redrawn no matter which fields are involved in tabbing.
</span></text>
</content>
<name></name>
<script></script>
</card>
card_11463.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
Figure 2 shows a case where a section of the card is reserved for an image that is different on each card. Possibilities are address or catalog stacks with a picture of the person or item on each card. For these stacks, having to put pencil dots at corners might be a bit of a pain. Another work-around that would be more suitable for this case is to use an optional rectangle parameter to specify that the area occupied by the pretty picture should always be drawn.
You would not want to use this work-around for the card in Figure 1 because it would mean that the six fields that were within the rectangle would also have to be drawn.</span></text>
</content>
<name></name>
<script></script>
</card>
card_11667.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">imitations and Workarounds </span><span class="style4">(cont.)</span></text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text><span class="style3">Apologies and Mumbles</span><span class="style1">
</span><span class="style6">
</span><span class="style5">The problems with card paint don't seem to occur if all fields are in the card layer: only when there are both background and card fields. It's a lot easier to make the symptoms appear when the card paint is opaque than when it is transparent.
The problems with the card paint are certainly disappointing. I have rough ideas of how these ideas could be avoided, but as a piece of "outsider code," I haven't been able to discover a clean way to incorporate the fixes into FastTab without relying too heavily on HyperCard internals.
The problems reduce FastTab's viability as an XCMD you might just stick in your Home stack and forget ΓÇö because there will be stacks that will cause problems ΓÇö but I think FastTab still succeeds in its initial goal: to produce tabbing acceleration on specific stacks that require many fields.
</span><span class="style6">
</span></text>
</content>
<name></name>
<script></script>
</card>
card_4987.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
To install FastTab, use one of the following techniques:
1) use ResEdit to copy the XCMD into the desired stack.
2) use the Resource Mover card that appears in the Power Tools stack (found in the 5 disk HyperCard version) to copy the XCMD.
3) add the command start using stack "FastTab Distribution Stack" to the openStack handler in your stack. This will add the FastTab stack to the user-definable inheritance path.
4) Use the new ResCopy XCMD once it is available. A beta version of ResCopy is now available on various electronic bulletin boards.</text>
</content>
<name>How to Install FastTab</name>
<script></script>
</card>
card_2338.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Compatibility with Future HyperCard Versions</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>The FastTab XCMD was created to overcome a major limitation of the current HyperCard implementation. The design of the XCMD is based on an analysis of the behaviour of HyperCard 2.0. It goes beyond the official XCMD interface and fools HyperCard into doing less work. This approach is similar to the approach taken by Startup documents (INITs) that modify the operation of the Mac.
FastTab may not work with future HyperCard versions. The most likely case will be that it no longer speeds up tabbing, either because a new HyperCard version is better tuned for tabbing or because the techniques used to fool HyperCard no longer work. The second most likely case is that portions of the screen would not be redrawn properly when the user presses the Tab key.</text>
</content>
<name>Compatibility with Future</name>
<script></script>
</card>
card_6591.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">ompatibility with Future HyperCard Versions</span><span class="style4"> (cont.)</span></text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>I would be surprised if the techniques used by FastTab would cause data loss or stack corruption (either in current or future HyperCard versions), but don't take my word for it. Stacks using FastTab (or any other XCMD) should be well-tested.
My hope is that future HyperCard versions will make FastTab irrelevant. As interesting as this exploration was, I prefer to create "assumptionless" XCMDs that stay strictly within the defined interface. Still, there are stacks for which tabbing speed is critical. Waiting for the next release was not a viable option.
FastTab has been tested with HyperCard 2.0, HyperCard 2.0v2, and HyperCard 2.1</text>
</content>
<name></name>
<script></script>
</card>
card_2080.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The FastTab XCMD has been designed specifically for HyperCard 2.0. While there are other programs that also use XCMDs, the FastTab XCMD most probably will not increase the speed of other programs. It is very likely, if the FastTab XCMD is called by another program, that sections of the window will not be redrawn.
Do not use FastTab with programs other than HyperCard 2.0.
</text>
</content>
<name>Compatibility with Other </name>
<script></script>
</card>
card_7173.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1"> believe that FastTab works properly. I do not believe that it will cause data loss or stack corruption, </span><span class="style11">but Symplex Systems is not liable for any incidental, consequential or indirect damages arising out of the use, or attempted use, of FastTab</span><span class="style1">. Test thoroughly any stack using FastTab. Once the stack is in use, follow an appropriate backup strategy to protect your data.
</span><span class="style6">
</span><span class="style1">If you use FastTab, you must agree to this exclusion of liability. You must also agree that, even if this exclusion is rejected for any reason, Symplex Systems' liability for any damages will not exceed the greater of $14 or the amount you have paid to Symplex Systems for the use of this software. If you cannot agree to this, don't register and don't use FastTab.
</span><span class="style6">That's as much pseudo-legalese as I can take. As any decent lawyer will tell you, common sense and goodwill beats litigation any day.</span></text>
